Adding a pipeline to trigger CT's workflow for uploading sources for new or updated components. It's meant to be triggered by each merge queue item.

Why an ADO pipeline instead of GitHub Actions: calling CT endpoints would require authentication secrets kept in GitHub and we want don't want that.

NOTES:

• .github/workflows/scripts/check_rendered_specs.py is temporary until feat: add sources upload pipeline #16656 is merged and I can switch to the version of that script from that PR.
• The pipeline won't fail for the time being until we know they are stable and can be marked as required.
• The pipeline is meant for non-fork PRs only - enabling forks require security hardening (out of scope for this PR).

Other work:

• Added AI instructions for how we want the ADO pipelines written.
• Refactored scripts into subdirectories for clearer grouping and to scope down the dependencies for each inside their requiremenets.txt files.